IoT Sparkplug EIE
The IoT Sparkplug EIE uses the MQTT protocol with the Sparkplug specification to subscribe to data that is published to the MQTT server. The IoT Sparkplug EIE must use the MQTT Comm EIE. The devices are non-functional without this exact combination. The EIE does not poll devices; it is a pub/sub protocol. The EIE subscribes to topics and the MQTT server publishes payloads on those topics. CygNet then parses the payload and processes the data. Like most CygNet EIEs, the IoT Sparkplug EIE is a template-driven EIE.
For more information,see Installing Link.
The IoT Sparkplug EIE uses the Sparkplug B version of the specification. It is capable of processing metric items with aliases, historical data, and null values.
This EIE does not support all features of the Sparkplug B specification:
- Complex objects as defined by the Sparkplug template data type are not supported.
- Arrays of records as defined by the DataSet data type are not supported.
- The metric components metadata and is_transient are not used.
- The metric component properties are not used, except for those where name = "units". Units are stored in the DDS transaction; "units" is used in point processing.
Specifications
The following table lists and describes EIE specifications.
|
Manufacturer |
Weatherford |
|
Protocol(s) |
MQTT |
|
Model(s) |
Various |
|
Required Files |
CxDdsIoTSparkplugEditors.dll UisIoTSparkplugDriver.dll or UisIoTSparkplugDriver64.dll |
|
Sample Templates |
IoTSparkplug_Sample.dtf IoTSparkplug_POC.dtf |
|
IoTSparkplug |
|
|
Cryout Support |
No |
|
FMS Support |
No |
|
Listen Mode |
No |
|
64-bit Support |
Yes. See 64-bit Device Drivers. |
For more information, see sample device template files and manufacturer documentation.
More:
